💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

@james-elastic I think it would be better to do it in this PR

I think there is no rush - 8.3 is still quite away. Who should we contact to get the mappings? Because the previous list didn't mention them.

@james-elastic and @melissaburpo

/test

🌐 Coverage report

/test

/test

@jsoriano it looks like we need to release a new revision of elastic-package with updated package-spec. Do you know if there are any blockers or if we can proceed with a release?

@jsoriano it looks like we need to release a new revision of elastic-package with updated package-spec. Do you know if there are any blockers or if we can proceed with a release?

Yes, we have to merge #3316 or similar first. We will also have to check some other new validations as the ones for the changelog links.

@Mergifyio rebase

rebase

❌ Base branch update has failed

Rebasing (1/16)
error: could not apply c4c34a7f... [Osquery] Add default saved queries
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply c4c34a7f... [Osquery] Add default saved queries
Auto-merging packages/osquery_manager/manifest.yml
CONFLICT (content): Merge conflict in packages/osquery_manager/manifest.yml

@tomsonpl As mergify failed rebasing, can you try rebasing it manually? Package Spec changes are merged now.

@mtojek yes, I will try rebasing manually. Thank you :)

@P1llus thank you :)